Contingency Management

This topic describes various scenarios where licenses can fail to work.

This topic discusses various situations that you may encounter while managing your Process Platform licenses. Few of such situations along with specific solutions are mentioned below.
License Key Expiration

The license key expiration is explained for various scenarios below:

• The demo license key is valid for only a trial period, after which it becomes invalid. In case the customer wishes to continue the use of the Applications, he is required to send a Usage Report to the Process Platform License Service, and obtain a new key. In case the customer does not send the Usage Report on time, the Service Containers cannot be started, and hence the customer cannot work with the Applications.
  
• The operational license key is supplied by the Process Platform License Service on receipt of a Usage Report. The customer is expected to send Usage Reports at regular intervals (monthly) to the Process Platform License Service and obtain these keys. In case the customer does not send the Usage Report on time, the customer will be allowed to continue using the Applications, but a warning is displayed during each transaction, stating that the license has expired. The user can either clickContinuein the dialog box to continue using the Applications with the warnings, or click onRenew Licenseto open the License Manager screen from where the license can be renewed.
  
  Note: Whenever the License Keys are updated by the Standalone/Master or through the Management Console, the OpenText Process Suite Platform (<instance name>)s and the Service Containers have to be re-started.
  
  Invalid Usage Report
  
  There could be different reasons for invalid Usage Reports being sent to Process Platform License Service. Depending on the reason for invalidity, the consequences would vary.
  
  The following are some instances and consequences of invalid Usage Reports being sent to Process Platform License Service:
  
  
• Contributor sends an old report to the Master- Since every report has a date and time stamp, the Master would recognize the report as an old one, and will not consolidate it. The Master Report will, therefore, not contain the details of that particular Contributor. When the Master report is sent to Process Platform License Service, the report is read, and License Keys are issued for all the Contributors of that report. Therefore, the Contributor that sent an old report will not receive a License Key.
  
• Contributor does not send the Usage Report to the Master- The Master Report will not contain the details of that particular Contributor. When the Master report is sent to Process Platform License Service, the report is read, and License Keys are issued for all the Contributors of that report. Therefore, the Contributor that did not send a Usage Report will not receive a License Key.
  
  Internet Failure
  
  In case of Internet failure (when the Usage Report cannot be sent directly to the Process Platform License Service through HTTP), the Usage Report has to be sent to the Process Platform License Service through mail. For this purpose, the Usage Report can be taken from the folder where it is stored. By default, the Usage Report would be stored in the folder specified below:
  
  
• Standalone or Contributor machine - The report is stored in <Process_Platform_Installation_Directory>\license\log\report
  
• Master machine - The master report is stored in <Process_Platform_install_dir\license\master\log\report>. The contributor reports are stored in <Process_Platform_Installation_Directory>\license\masterstore
  
  The user can change the default folder (<Process_Platform_Installation_Directory>) for storing the Usage Report by changing the corresponding property in the wcp.properties file. The property to be changed in each case is given below:
  
  
• Standalone or Contributor machine - The folder to be specified in com.eibus.license.LogDir.report
  
• Master machine - The folder for Master reports to be specified in com.eibus.license.MasterLogDir.report. The folder for Contributor reports to be specified in com.eibus.license.LicMasterStoreDir
  
  Once the Usage Report has been sent, the License Key has to be obtained in a similar manner and updated using the License Configuration Tool of the Management Console.
  
  Master Machine Breakdown
  
  When the Master machine breaks down (crashes), one of the Contributors needs to be made the Master. To do this, the following steps have to be executed:
  
  

1. Ensure that the user has got administrative privileges in the machine that has to be configured as Master
   
2. Create the following directory structure under Process Platform Installation Directory:
   
   

• Process_Platform_install_dir>\license\master\log\report
  
• Process_Platform_install_dir>\license\master\log\key
  
• Process_Platform_install_dir>\license\masterstore
  
  

1. Create a file called contributors.xml in the masterstore directory as follows
   <contributors> <contributor> <machine>master machine name</machine> </contributor> </contributors>
   
2. Attach the Method Set LicenseMaster of Process Platform ESB Server to the Monitor Service Group. Restart the Monitor.
   
3. Go to wcp.properties and set the property com.eibus.web.license.LicReportGateway.licuser to the id of the user who is the administrator in both Process Platform and the current machine.
   
4. Go to the Management Console and click Content Management. In the attribute licenseconfig of the entry licinfo, change the <type> to master.
   
5. Go to the License Configuration Tool of Management Console of the Master and Contributors and change the name of the Master machine. Save all changes made
   
6. Inform other Contributors about the identity of the new Master.
   
7. Obtain the current/latest License Keys for all Contributors from the Process Platform License Service.